Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b77d97cb29558c362451a7f50e6d3ca547decd5215af21903196467ac954239c

Tx prefix hash: 61e2c4cc52c324b90506da60001af196be8e68156d1e1d7d6c107de1bfcb14dc
Tx public key: 6c73dc478cffbab66672bea981b6a2e41dd57016f06884d4ad749a155b3ad34e
Timestamp: 1577787109 Timestamp [UCT]: 2019-12-31 10:11:49 Age [y:d:h:m:s]: 04:324:17:26:15
Block: 35624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121228 RingCT/type: yes/0
Extra: 016c73dc478cffbab66672bea981b6a2e41dd57016f06884d4ad749a155b3ad34e021100000012d81c26c0000000000000000000

1 output(s) for total of 467.696105781000 dcy

stealth address amount amount idx
00: b971f677ccb4b9ef7b961d885c611c51085f7fb2d67106634b06951ba7ea7f20 467.696105781000 60131 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": 35634, "vin": [ { "gen": { "height": 35624 } } ], "vout": [ { "amount": 467696105781, "target": { "key": "b971f677ccb4b9ef7b961d885c611c51085f7fb2d67106634b06951ba7ea7f20" } } ], "extra": [ 1, 108, 115, 220, 71, 140, 255, 186, 182, 102, 114, 190, 169, 129, 182, 162, 228, 29, 213, 112, 22, 240, 104, 132, 212, 173, 116, 154, 21, 91, 58, 211, 78, 2, 17, 0, 0, 0, 18, 216, 28, 38, 192, 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