Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9fd7b7bb21679eb4f3735dec78dcefe69d3a89da430b7a9ac5df1c03f0b5b3d

Tx prefix hash: 6929393e0ce72b74a1ab7e61bb051a59cce78b8c2563d67e31c72f7b6c228b1c
Tx public key: e176f85a172a1d4743412a90f2815c4ff38a3b94f67c4931b1aa48c229e9c1b1
Timestamp: 1732739074 Timestamp [UCT]: 2024-11-27 20:24:34 Age [y:d:h:m:s]: 00:131:16:20:22
Block: 1163065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93914 RingCT/type: yes/0
Extra: 01e176f85a172a1d4743412a90f2815c4ff38a3b94f67c4931b1aa48c229e9c1b10211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a86016e1bcb85df83f1b6a0b0d1aa87dc52984009951b838f031b9020a8802cf 0.600000000000 1648730 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": 1163075, "vin": [ { "gen": { "height": 1163065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a86016e1bcb85df83f1b6a0b0d1aa87dc52984009951b838f031b9020a8802cf" } } ], "extra": [ 1, 225, 118, 248, 90, 23, 42, 29, 71, 67, 65, 42, 144, 242, 129, 92, 79, 243, 138, 59, 148, 246, 124, 73, 49, 177, 170, 72, 194, 41, 233, 193, 177, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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