Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ed0bf2be7a53b0cf5ddada8f76cbfb9519f47f3022484acb31fe4404f14347c

Tx prefix hash: 52832b217f45022a85d0ae2b95f08ce1c77ff27f21c7f2ab353055f751f7a0a8
Tx public key: 5992ede257a03c74e5aaafc56e7d6dcdc8f2c8ca4251914c4da831cbca8f5a34
Timestamp: 1577478094 Timestamp [UCT]: 2019-12-27 20:21:34 Age [y:d:h:m:s]: 05:311:03:01:35
Block: 33070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1369898 RingCT/type: yes/0
Extra: 015992ede257a03c74e5aaafc56e7d6dcdc8f2c8ca4251914c4da831cbca8f5a340211000000124ac5aa02000000000000000000

1 output(s) for total of 476.898789171000 dcy

stealth address amount amount idx
00: 2d5718bdcb7bf9f578bf379ae8bee6018b2167c6f79f5c82939b9d92675ae1ed 476.898789171000 55205 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": 33080, "vin": [ { "gen": { "height": 33070 } } ], "vout": [ { "amount": 476898789171, "target": { "key": "2d5718bdcb7bf9f578bf379ae8bee6018b2167c6f79f5c82939b9d92675ae1ed" } } ], "extra": [ 1, 89, 146, 237, 226, 87, 160, 60, 116, 229, 170, 175, 197, 110, 125, 109, 205, 200, 242, 200, 202, 66, 81, 145, 76, 77, 168, 49, 203, 202, 143, 90, 52, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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