Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5db39e06d37ed6d288a82710a73d338deee9b7f2cc469f908c2d0e4e7031cf91

Tx prefix hash: b913f301389aa385aa748b24a94ec964467bdf90c8896dbe38a9be3d0daedd50
Tx public key: 756a5266fc15c542fba318be47ca853db897ff866f5b90af89a4fb8c86a19d79
Timestamp: 1698503788 Timestamp [UCT]: 2023-10-28 14:36:28 Age [y:d:h:m:s]: 01:159:11:20:06
Block: 879556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374963 RingCT/type: yes/0
Extra: 01756a5266fc15c542fba318be47ca853db897ff866f5b90af89a4fb8c86a19d7902110000000333af99f4000000000000000000

1 output(s) for total of 0.747594098000 dcy

stealth address amount amount idx
00: 90a826687ebeec0b0b9ec596e57ed5d77617e943cbd976257477f96b0fc6d34f 0.747594098000 1335086 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": 879566, "vin": [ { "gen": { "height": 879556 } } ], "vout": [ { "amount": 747594098, "target": { "key": "90a826687ebeec0b0b9ec596e57ed5d77617e943cbd976257477f96b0fc6d34f" } } ], "extra": [ 1, 117, 106, 82, 102, 252, 21, 197, 66, 251, 163, 24, 190, 71, 202, 133, 61, 184, 151, 255, 134, 111, 91, 144, 175, 137, 164, 251, 140, 134, 161, 157, 121, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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