Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b235b1bb31e2bc4eaefa9f197feefcb18b4cebd0598a1acb36404195dcb1f48

Tx prefix hash: f405086f4ad54c74191a25871c120f4766d4a6f33fa196e9eda1db3455c35c29
Tx public key: ed891b076b29b4ba30687a629bcacad71379260bc975396abf7696fcc4134b1e
Timestamp: 1732061223 Timestamp [UCT]: 2024-11-20 00:07:03 Age [y:d:h:m:s]: 00:147:18:34:25
Block: 1157460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105432 RingCT/type: yes/0
Extra: 01ed891b076b29b4ba30687a629bcacad71379260bc975396abf7696fcc4134b1e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b35ac78666d3cb78ec7dc1df6c16d99f0c6ecb54cc7960c960b412d9549d6f34 0.600000000000 1643083 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": 1157470, "vin": [ { "gen": { "height": 1157460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b35ac78666d3cb78ec7dc1df6c16d99f0c6ecb54cc7960c960b412d9549d6f34" } } ], "extra": [ 1, 237, 137, 27, 7, 107, 41, 180, 186, 48, 104, 122, 98, 155, 202, 202, 215, 19, 121, 38, 11, 201, 117, 57, 106, 191, 118, 150, 252, 196, 19, 75, 30, 2, 17, 0, 0, 0, 2, 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