Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2e1eb670d5347c2b3b63b76e85b10164803bad7431590b8dbd68284ca9e594d

Tx prefix hash: 5575a46aba665a5db4ab1589366ab52ff07258d8e9919a9dacbe82ba0d4b7d93
Tx public key: edc177c304327718ef0ad5e8e52f947dd7e418d3c5570cdb332c3c858450cb4f
Timestamp: 1735356832 Timestamp [UCT]: 2024-12-28 03:33:52 Age [y:d:h:m:s]: 00:170:04:14:47
Block: 1184738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121360 RingCT/type: yes/0
Extra: 01edc177c304327718ef0ad5e8e52f947dd7e418d3c5570cdb332c3c858450cb4f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50f913fe5cb58cbde6a5ad42b0ab21899ac3d77f2e56d6b56b3bfa713d7d5347 0.600000000000 1671197 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": 1184748, "vin": [ { "gen": { "height": 1184738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50f913fe5cb58cbde6a5ad42b0ab21899ac3d77f2e56d6b56b3bfa713d7d5347" } } ], "extra": [ 1, 237, 193, 119, 195, 4, 50, 119, 24, 239, 10, 213, 232, 229, 47, 148, 125, 215, 228, 24, 211, 197, 87, 12, 219, 51, 44, 60, 133, 132, 80, 203, 79, 2, 17, 0, 0, 0, 4, 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