Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9665d33dd492c654147a0d47d191286b2db0ba0737c7210a58f6bb8464e00bb

Tx prefix hash: bbdb273aedc0383ac6fae70ceae16f94e459fdfa8c5d2f02892bd31f35d0828c
Tx public key: cb86ea66df5d0ee93c12b728b9708295102db04da4cc7367a0c2fd43f291c8be
Timestamp: 1574736251 Timestamp [UCT]: 2019-11-26 02:44:11 Age [y:d:h:m:s]: 05:345:03:50:28
Block: 17602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1387007 RingCT/type: yes/0
Extra: 01cb86ea66df5d0ee93c12b728b9708295102db04da4cc7367a0c2fd43f291c8be0211000000010b4dd45a000000000000000000

1 output(s) for total of 536.633953310000 dcy

stealth address amount amount idx
00: 669ba0409cbfc6f0c3813572c00fb2583362b3a62956efccfbe3cf6faea7ed3b 536.633953310000 25818 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": 17612, "vin": [ { "gen": { "height": 17602 } } ], "vout": [ { "amount": 536633953310, "target": { "key": "669ba0409cbfc6f0c3813572c00fb2583362b3a62956efccfbe3cf6faea7ed3b" } } ], "extra": [ 1, 203, 134, 234, 102, 223, 93, 14, 233, 60, 18, 183, 40, 185, 112, 130, 149, 16, 45, 176, 77, 164, 204, 115, 103, 160, 194, 253, 67, 242, 145, 200, 190, 2, 17, 0, 0, 0, 1, 11, 77, 212, 90, 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