Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d168ae9d647ebfd04a6e4b9d00f3fa16079938aacf3c842d9df5ccbd6851ac83

Tx prefix hash: 297f2749afdd3ea43c4cc5e0c2697569724421935af940fd8f1bb40b5c83cb3c
Tx public key: c3bdc24e6236a9514f5fa3406850750f0fecdeae8af05ee088361625c2564550
Timestamp: 1657745758 Timestamp [UCT]: 2022-07-13 20:55:58 Age [y:d:h:m:s]: 02:250:17:46:47
Block: 543123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700371 RingCT/type: yes/0
Extra: 01c3bdc24e6236a9514f5fa3406850750f0fecdeae8af05ee088361625c25645500211000000075eb576c5000000000000000000

1 output(s) for total of 9.736619138000 dcy

stealth address amount amount idx
00: 4fbdcd43f5909c36622f19dcf805b22d2b9ed6e563da8f0b7cb0e51bff70c88b 9.736619138000 973758 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": 543133, "vin": [ { "gen": { "height": 543123 } } ], "vout": [ { "amount": 9736619138, "target": { "key": "4fbdcd43f5909c36622f19dcf805b22d2b9ed6e563da8f0b7cb0e51bff70c88b" } } ], "extra": [ 1, 195, 189, 194, 78, 98, 54, 169, 81, 79, 95, 163, 64, 104, 80, 117, 15, 15, 236, 222, 174, 138, 240, 94, 224, 136, 54, 22, 37, 194, 86, 69, 80, 2, 17, 0, 0, 0, 7, 94, 181, 118, 197, 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