Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9506dac35d64774db88c2d94d165a528d795db823860c2b549e185441a9a9ab0

Tx prefix hash: 6a9c3478c4ff21fd13e8dcbd45d4a0413d5f5e6c284ef8e9a88bf624cb0b0883
Tx public key: 0665a72c4b65071206b12dc67646e88e7e1114726a4cbedc9987f6068de96fb5
Timestamp: 1727066200 Timestamp [UCT]: 2024-09-23 04:36:40 Age [y:d:h:m:s]: 00:265:06:46:11
Block: 1116137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189364 RingCT/type: yes/0
Extra: 010665a72c4b65071206b12dc67646e88e7e1114726a4cbedc9987f6068de96fb502110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2549886db34e8a500a8f93ae90c63e1b084ca3c3630513bbfd361ef273a9d054 0.600000000000 1596516 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": 1116147, "vin": [ { "gen": { "height": 1116137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2549886db34e8a500a8f93ae90c63e1b084ca3c3630513bbfd361ef273a9d054" } } ], "extra": [ 1, 6, 101, 167, 44, 75, 101, 7, 18, 6, 177, 45, 198, 118, 70, 232, 142, 126, 17, 20, 114, 106, 76, 190, 220, 153, 135, 246, 6, 141, 233, 111, 181, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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