Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366a8dae8cd3b77b203569eebaafc4968e1ce886479641b992948c7cedb157f5

Tx prefix hash: cb04ac575e0e0be2d63fb0a2184b93aaa3a246c7f71b084427cecbace6b31b1d
Tx public key: 8e384012ea2957eee815dc19d252ea8dfb0f6a06af2b432c8d9311f9df790d34
Timestamp: 1734680136 Timestamp [UCT]: 2024-12-20 07:35:36 Age [y:d:h:m:s]: 00:104:18:01:25
Block: 1179170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74623 RingCT/type: yes/0
Extra: 018e384012ea2957eee815dc19d252ea8dfb0f6a06af2b432c8d9311f9df790d340211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 817a8fde65c816ec1cb9554ab51be4d9b4ff18e3e454c4858c66b4fa58f2fd03 0.600000000000 1665561 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": 1179180, "vin": [ { "gen": { "height": 1179170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "817a8fde65c816ec1cb9554ab51be4d9b4ff18e3e454c4858c66b4fa58f2fd03" } } ], "extra": [ 1, 142, 56, 64, 18, 234, 41, 87, 238, 232, 21, 220, 25, 210, 82, 234, 141, 251, 15, 106, 6, 175, 43, 67, 44, 141, 147, 17, 249, 223, 121, 13, 52, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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