Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1209b3112c5fdb09440f22e13c6a70868c08323f9a7d2091fe82e4606b84bd

Tx prefix hash: ac0b1e1c2170be6f4e529aecbeb0f88fc15da186e55c019923449d1e2ca8a210
Tx public key: 26ac989aece78738227b47a6ea9c8571ec3f029cce4b55ed440c896f9bb0897f
Timestamp: 1702277446 Timestamp [UCT]: 2023-12-11 06:50:46 Age [y:d:h:m:s]: 01:334:08:43:58
Block: 910620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497828 RingCT/type: yes/0
Extra: 0126ac989aece78738227b47a6ea9c8571ec3f029cce4b55ed440c896f9bb0897f021100000011faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6506a7360a99934c4ebc3f19faadb8acd6511fa608a1e688df0ade181d6f963 0.600000000000 1367781 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": 910630, "vin": [ { "gen": { "height": 910620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6506a7360a99934c4ebc3f19faadb8acd6511fa608a1e688df0ade181d6f963" } } ], "extra": [ 1, 38, 172, 152, 154, 236, 231, 135, 56, 34, 123, 71, 166, 234, 156, 133, 113, 236, 63, 2, 156, 206, 75, 85, 237, 68, 12, 137, 111, 155, 176, 137, 127, 2, 17, 0, 0, 0, 17, 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