Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3deaeb2decd8cf4b61cb8566395cea34a2675424c7a9e5c94af0a0b151c95c4d

Tx prefix hash: 6af08c6c608b2ebfce2c0795ec75701aa103ea4fc5afb38cf867f3c6734a91e6
Tx public key: d3f5c8d9dbb532a7b506dfb24a46e580c8bb2f57d9db6908afacc91e4589ddd9
Timestamp: 1637525365 Timestamp [UCT]: 2021-11-21 20:09:25 Age [y:d:h:m:s]: 03:345:00:45:43
Block: 379185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1022994 RingCT/type: yes/0
Extra: 01d3f5c8d9dbb532a7b506dfb24a46e580c8bb2f57d9db6908afacc91e4589ddd902110000001ce59f5d07000000000000000000

1 output(s) for total of 34.009721043000 dcy

stealth address amount amount idx
00: b7bd505db7718e1a43ec0d70bf6c87591e31c3346e4b48fbfd18a856f9484573 34.009721043000 766567 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": 379195, "vin": [ { "gen": { "height": 379185 } } ], "vout": [ { "amount": 34009721043, "target": { "key": "b7bd505db7718e1a43ec0d70bf6c87591e31c3346e4b48fbfd18a856f9484573" } } ], "extra": [ 1, 211, 245, 200, 217, 219, 181, 50, 167, 181, 6, 223, 178, 74, 70, 229, 128, 200, 187, 47, 87, 217, 219, 105, 8, 175, 172, 201, 30, 69, 137, 221, 217, 2, 17, 0, 0, 0, 28, 229, 159, 93, 7, 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