Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ceeedc6421f13587d3449d8b2d1c91a09fa0bea732d241d60d1f98641d49a578

Tx prefix hash: 3d6c2ce78a1701e3ddf3ebf806d1c657c0f9a2db2eaf898df97c1cee6db7e1b3
Tx public key: 0ee5482b54a4887d2cf6e4b5d24f53a9ce052d70747a4afb08a9f3949d7a6111
Timestamp: 1705301544 Timestamp [UCT]: 2024-01-15 06:52:24 Age [y:d:h:m:s]: 01:130:06:46:04
Block: 935672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354260 RingCT/type: yes/0
Extra: 010ee5482b54a4887d2cf6e4b5d24f53a9ce052d70747a4afb08a9f3949d7a61110211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fff47cbbee924d9d12e2d315c4b037aacdb5971f453478e2e43357b2b355e663 0.600000000000 1393688 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": 935682, "vin": [ { "gen": { "height": 935672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fff47cbbee924d9d12e2d315c4b037aacdb5971f453478e2e43357b2b355e663" } } ], "extra": [ 1, 14, 229, 72, 43, 84, 164, 136, 125, 44, 246, 228, 181, 210, 79, 83, 169, 206, 5, 45, 112, 116, 122, 74, 251, 8, 169, 243, 148, 157, 122, 97, 17, 2, 17, 0, 0, 0, 3, 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