Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe216b8d8b1033741adb4cd307e78b5febca7879f8cf45acf3641a23cb94263

Tx prefix hash: 294e1485f567e774728076c3c29ac40baed51a5a760ef61f9410def167522107
Tx public key: e52876751e594ff99c15d868fe3ecee2caf5f47a47a9b2cf64bfe82e28d5613f
Timestamp: 1742906861 Timestamp [UCT]: 2025-03-25 12:47:41 Age [y:d:h:m:s]: 00:254:20:40:30
Block: 1246981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179919 RingCT/type: yes/0
Extra: 01e52876751e594ff99c15d868fe3ecee2caf5f47a47a9b2cf64bfe82e28d5613f021100000001c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b10a97ae0e734303fcd277dd28e3f87519acca3d8ff9c1a5be40951b1cbd32 0.600000000000 1733982 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": 1246991, "vin": [ { "gen": { "height": 1246981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b10a97ae0e734303fcd277dd28e3f87519acca3d8ff9c1a5be40951b1cbd32" } } ], "extra": [ 1, 229, 40, 118, 117, 30, 89, 79, 249, 156, 21, 216, 104, 254, 62, 206, 226, 202, 245, 244, 122, 71, 169, 178, 207, 100, 191, 232, 46, 40, 213, 97, 63, 2, 17, 0, 0, 0, 1, 198, 116, 9, 88, 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