Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72c3901c0a25e7c85093803927924f047e2cac1e0fbffe337663640872fd5de5

Tx prefix hash: e9f7f7200d2b39c5f665eaacbd73d6944017ed48d2ce8e2ca96f7a4255dbfc3b
Tx public key: 9908836d4aff1ac29b11d6dcf4d8d5c604479271dbcda0a6e41dd5cbf8dbd6a4
Timestamp: 1719385201 Timestamp [UCT]: 2024-06-26 07:00:01 Age [y:d:h:m:s]: 00:261:17:52:21
Block: 1052451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187042 RingCT/type: yes/0
Extra: 019908836d4aff1ac29b11d6dcf4d8d5c604479271dbcda0a6e41dd5cbf8dbd6a40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbf26690e36d7f214368340713a409efde53cbf738ef8e4bcf12a73857467230 0.600000000000 1522778 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": 1052461, "vin": [ { "gen": { "height": 1052451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf26690e36d7f214368340713a409efde53cbf738ef8e4bcf12a73857467230" } } ], "extra": [ 1, 153, 8, 131, 109, 74, 255, 26, 194, 155, 17, 214, 220, 244, 216, 213, 198, 4, 71, 146, 113, 219, 205, 160, 166, 228, 29, 213, 203, 248, 219, 214, 164, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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