Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834720d0cf57ca48d50f95c61c3c2a63968b29a4a3f53dbfc6fd1993ba75b11c

Tx prefix hash: b79f5dc5a10db461466c4a22e9f818758a64c473e578479ef2cc949cb109e1fd
Tx public key: bd48209e03a3597aaf2b24df5f9c2e176dca3ba6899a9c22072cb19aa8ae6afb
Timestamp: 1694404296 Timestamp [UCT]: 2023-09-11 03:51:36 Age [y:d:h:m:s]: 01:227:02:16:29
Block: 845537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423426 RingCT/type: yes/0
Extra: 01bd48209e03a3597aaf2b24df5f9c2e176dca3ba6899a9c22072cb19aa8ae6afb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.969136573000 dcy

stealth address amount amount idx
00: 70039bb9b297796621f71058960ed7be71d058ef74d8da9854548c8de605af9d 0.969136573000 1298931 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": 845547, "vin": [ { "gen": { "height": 845537 } } ], "vout": [ { "amount": 969136573, "target": { "key": "70039bb9b297796621f71058960ed7be71d058ef74d8da9854548c8de605af9d" } } ], "extra": [ 1, 189, 72, 32, 158, 3, 163, 89, 122, 175, 43, 36, 223, 95, 156, 46, 23, 109, 202, 59, 166, 137, 154, 156, 34, 7, 44, 177, 154, 168, 174, 106, 251, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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