Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb871c3b3812d830c887cd9eff4cbe34e5fde5cf5c4d30938444040a71a4223

Tx prefix hash: 3788d978ac4fec0f9fc21dfc5aafd3b49263584b8246ffa9aaeb3fdcbad25d6e
Tx public key: a2e496aacbdb97a0246fa6cf235b54425821a6020ca44b0ae3e97b20a07a20f4
Timestamp: 1705292097 Timestamp [UCT]: 2024-01-15 04:14:57 Age [y:d:h:m:s]: 01:358:07:34:11
Block: 935591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515000 RingCT/type: yes/0
Extra: 01a2e496aacbdb97a0246fa6cf235b54425821a6020ca44b0ae3e97b20a07a20f40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32aad1ee1648bbf5196a3f8323fd113c9789f2d51d1c0ee39ebc20b09d91a8e5 0.600000000000 1393607 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": 935601, "vin": [ { "gen": { "height": 935591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32aad1ee1648bbf5196a3f8323fd113c9789f2d51d1c0ee39ebc20b09d91a8e5" } } ], "extra": [ 1, 162, 228, 150, 170, 203, 219, 151, 160, 36, 111, 166, 207, 35, 91, 84, 66, 88, 33, 166, 2, 12, 164, 75, 10, 227, 233, 123, 32, 160, 122, 32, 244, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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