Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe873c1a0f8faec7e69fbd4274241cf2ad85737fa71cf9f8d4946a1bc8a0fe15

Tx prefix hash: 1d8d521ae0f8d2d69ae35a79109c291c1158ea555ff57eb3d6090398240ea44f
Tx public key: 856ea801bac4a6ce1af4d4123853cb7e743d1664cc90a4c61017e7c79097c6c1
Timestamp: 1699479039 Timestamp [UCT]: 2023-11-08 21:30:39 Age [y:d:h:m:s]: 01:130:03:46:20
Block: 887431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354217 RingCT/type: yes/0
Extra: 01856ea801bac4a6ce1af4d4123853cb7e743d1664cc90a4c61017e7c79097c6c1021100000008faf35c9c000000000000000000

1 output(s) for total of 0.704000080000 dcy

stealth address amount amount idx
00: b7f0557841cd80ba6e354206e8c7ea56137f984ea8b8e61a3aef4201fffa20e1 0.704000080000 1343314 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": 887441, "vin": [ { "gen": { "height": 887431 } } ], "vout": [ { "amount": 704000080, "target": { "key": "b7f0557841cd80ba6e354206e8c7ea56137f984ea8b8e61a3aef4201fffa20e1" } } ], "extra": [ 1, 133, 110, 168, 1, 186, 196, 166, 206, 26, 244, 212, 18, 56, 83, 203, 126, 116, 61, 22, 100, 204, 144, 164, 198, 16, 23, 231, 199, 144, 151, 198, 193, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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