Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9c582778fa0129346f59bbee5685fb4ee1406dcff9c8c2069ac30c7088dd446c

Tx prefix hash: 20e9d51c3a56e711df07d1c3af9909cee1082c791912cd64aadb63188d1f6794
Tx public key: 022749a6276e89360eac0ff7ebea7d60a8587df75e350d5d0891729e367a7bc6
Timestamp: 1708123404 Timestamp [UCT]: 2024-02-16 22:43:24 Age [y:d:h:m:s]: 01:008:18:51:00
Block: 959087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267279 RingCT/type: yes/0
Extra: 01022749a6276e89360eac0ff7ebea7d60a8587df75e350d5d0891729e367a7bc602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd0db54a5cefd1618906b56e958a29fd75addfb2b6d516e5613cae15a82a99e7 0.600000000000 1418616 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 959097, "vin": [ { "gen": { "height": 959087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd0db54a5cefd1618906b56e958a29fd75addfb2b6d516e5613cae15a82a99e7" } } ], "extra": [ 1, 2, 39, 73, 166, 39, 110, 137, 54, 14, 172, 15, 247, 235, 234, 125, 96, 168, 88, 125, 247, 94, 53, 13, 93, 8, 145, 114, 158, 54, 122, 123, 198, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8