Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf5dba0e4fa2a4cc12ea730c633b8ff727b455a4deacee19930ca5ece34ec77

Tx prefix hash: de551b0877b70d3f5d6830a206eddc8bf7fb62763e408c9d74592fd4da8a93a3
Tx public key: 2ffbfd64ed2143d96b792061dd97509c11d27b9196fb287e85354f91ed8750fc
Timestamp: 1728126597 Timestamp [UCT]: 2024-10-05 11:09:57 Age [y:d:h:m:s]: 00:180:08:41:55
Block: 1124930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128688 RingCT/type: yes/0
Extra: 012ffbfd64ed2143d96b792061dd97509c11d27b9196fb287e85354f91ed8750fc02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a40c4dfdeccdd1f48de9a1e3d64eb0e8798b537d967b2835ac3c046e32fc0a4 0.600000000000 1607603 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": 1124940, "vin": [ { "gen": { "height": 1124930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a40c4dfdeccdd1f48de9a1e3d64eb0e8798b537d967b2835ac3c046e32fc0a4" } } ], "extra": [ 1, 47, 251, 253, 100, 237, 33, 67, 217, 107, 121, 32, 97, 221, 151, 80, 156, 17, 210, 123, 145, 150, 251, 40, 126, 133, 53, 79, 145, 237, 135, 80, 252, 2, 17, 0, 0, 0, 2, 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