Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7514606d46e61a8765f2b13c184a0b33435657d98847450d6d70fb844ba043e

Tx prefix hash: 2390bc5d243a2ed07cf8e2ef5292b385e9d61644e5d864db88e9da40e02c8d7a
Tx public key: bdb6e89a0a5a80094ee0bcf00d175790925442bf9b01272c43e559a69a7b9a5c
Timestamp: 1737438405 Timestamp [UCT]: 2025-01-21 05:46:45 Age [y:d:h:m:s]: 00:150:18:25:39
Block: 1201935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107459 RingCT/type: yes/0
Extra: 01bdb6e89a0a5a80094ee0bcf00d175790925442bf9b01272c43e559a69a7b9a5c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eadffc1f64bf0e6927ae5366791a43270eeb2f218d39ec57d0ee0aef2061891c 0.600000000000 1688594 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": 1201945, "vin": [ { "gen": { "height": 1201935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eadffc1f64bf0e6927ae5366791a43270eeb2f218d39ec57d0ee0aef2061891c" } } ], "extra": [ 1, 189, 182, 232, 154, 10, 90, 128, 9, 78, 224, 188, 240, 13, 23, 87, 144, 146, 84, 66, 191, 155, 1, 39, 44, 67, 229, 89, 166, 154, 123, 154, 92, 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