Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12c8e21bfdf5b57d285c8db61261dc2e8b8b9f4508704c3be0c2494f93c060a3

Tx prefix hash: b54b4490af2545a64b074a0c4aa89ceba4afc1cfaa83cf602f7c5845e4b68fc9
Tx public key: b3644d23c0e91eb16534021a456d69bb7729eebc2531cfa49222706cb646029f
Timestamp: 1735001744 Timestamp [UCT]: 2024-12-24 00:55:44 Age [y:d:h:m:s]: 00:090:00:26:47
Block: 1181817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64101 RingCT/type: yes/0
Extra: 01b3644d23c0e91eb16534021a456d69bb7729eebc2531cfa49222706cb646029f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d6cfe42ae79c0fe0dddce3c75650a3f9c3daa7fd23cf82a42deff43fdd1a41f 0.600000000000 1668244 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": 1181827, "vin": [ { "gen": { "height": 1181817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d6cfe42ae79c0fe0dddce3c75650a3f9c3daa7fd23cf82a42deff43fdd1a41f" } } ], "extra": [ 1, 179, 100, 77, 35, 192, 233, 30, 177, 101, 52, 2, 26, 69, 109, 105, 187, 119, 41, 238, 188, 37, 49, 207, 164, 146, 34, 112, 108, 182, 70, 2, 159, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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