Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36c11879c1ecbdba1d1ff0338afd78f077b4759b7518b6b61af0985e9cb6610

Tx prefix hash: 52eb904e2a31333fd45ab05ec42d6c89c89fec89d10ead1b9d3a2c24ad6e380e
Tx public key: f8b729667caf887cc68c257c28b37691ad3ea9ab067c81aa52e66274a401736e
Timestamp: 1728827353 Timestamp [UCT]: 2024-10-13 13:49:13 Age [y:d:h:m:s]: 00:196:08:48:05
Block: 1130749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140134 RingCT/type: yes/0
Extra: 01f8b729667caf887cc68c257c28b37691ad3ea9ab067c81aa52e66274a401736e02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8fff23ddf1720b038c678dbe0186d366b4a8ea2aab9081aa9739bdb039e7630 0.600000000000 1613628 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": 1130759, "vin": [ { "gen": { "height": 1130749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8fff23ddf1720b038c678dbe0186d366b4a8ea2aab9081aa9739bdb039e7630" } } ], "extra": [ 1, 248, 183, 41, 102, 124, 175, 136, 124, 198, 140, 37, 124, 40, 179, 118, 145, 173, 62, 169, 171, 6, 124, 129, 170, 82, 230, 98, 116, 164, 1, 115, 110, 2, 17, 0, 0, 0, 13, 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