Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 104d29b4d7b0716792572b4f1c33bd44d840f9c21b36d78a0d6633e02dd74fe7

Tx prefix hash: 9cd72747abe70de9ff25d2fc96cf53e3034863ce0a41ea357b7e7b9edc87e8fc
Tx public key: 17aae4dc0f1b0e4ced12720b76b291a5907588e469bf1b23ac7321e8d2d31644
Timestamp: 1722500366 Timestamp [UCT]: 2024-08-01 08:19:26 Age [y:d:h:m:s]: 00:260:14:07:07
Block: 1078286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186154 RingCT/type: yes/0
Extra: 0117aae4dc0f1b0e4ced12720b76b291a5907588e469bf1b23ac7321e8d2d3164402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d92435fffc11d8918993ccc5254b640041a7ee0ad0b6ab18a0ea68f17c9fdbf3 0.600000000000 1550863 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": 1078296, "vin": [ { "gen": { "height": 1078286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d92435fffc11d8918993ccc5254b640041a7ee0ad0b6ab18a0ea68f17c9fdbf3" } } ], "extra": [ 1, 23, 170, 228, 220, 15, 27, 14, 76, 237, 18, 114, 11, 118, 178, 145, 165, 144, 117, 136, 228, 105, 191, 27, 35, 172, 115, 33, 232, 210, 211, 22, 68, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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