Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc1a65563c240f02271c411c5327b7fd49eb988a74c3d4e785625376114c7cca

Tx prefix hash: 43a24ff8f1d5dc15e2949f3ea1a55f0e2fef50b129c6e8ca219bd534cdab3e3d
Tx public key: cb32e3072d2ae08ffe2cdee0afe53d3c45905ce6676d23ebb38a27524a1c804a
Timestamp: 1577620334 Timestamp [UCT]: 2019-12-29 11:52:14 Age [y:d:h:m:s]: 04:333:14:02:46
Block: 34334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127466 RingCT/type: yes/0
Extra: 01cb32e3072d2ae08ffe2cdee0afe53d3c45905ce6676d23ebb38a27524a1c804a02110000003c8a2ee0d9000000000000000000

1 output(s) for total of 472.321876482000 dcy

stealth address amount amount idx
00: 2fc34cff975af7c6be7397559aaef5119c712b2517dd34d33f17c79a03dee4c1 472.321876482000 57751 of 0

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": 34344, "vin": [ { "gen": { "height": 34334 } } ], "vout": [ { "amount": 472321876482, "target": { "key": "2fc34cff975af7c6be7397559aaef5119c712b2517dd34d33f17c79a03dee4c1" } } ], "extra": [ 1, 203, 50, 227, 7, 45, 42, 224, 143, 254, 44, 222, 224, 175, 229, 61, 60, 69, 144, 92, 230, 103, 109, 35, 235, 179, 138, 39, 82, 74, 28, 128, 74, 2, 17, 0, 0, 0, 60, 138, 46, 224, 217, 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