Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0abb169442d8f4db787e94df46696e5977afb8d856db9a8dd7c4e2fd0fdfcba6

Tx prefix hash: bc37db38690ffbf24c57b4e1f7659f1e3919c28cbaefedf0779bb677d42eff14
Tx public key: d5e8e469a2b85c59612b325ab1a52f83b24326ee5553a2e268d8d5e34d5e3fc5
Timestamp: 1706729767 Timestamp [UCT]: 2024-01-31 19:36:07 Age [y:d:h:m:s]: 01:283:00:06:37
Block: 947516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461067 RingCT/type: yes/0
Extra: 01d5e8e469a2b85c59612b325ab1a52f83b24326ee5553a2e268d8d5e34d5e3fc502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 266508848099a6eaa0288a846d14544a77aed4a3573689f5078893b890076b3f 0.600000000000 1405868 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": 947526, "vin": [ { "gen": { "height": 947516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "266508848099a6eaa0288a846d14544a77aed4a3573689f5078893b890076b3f" } } ], "extra": [ 1, 213, 232, 228, 105, 162, 184, 92, 89, 97, 43, 50, 90, 177, 165, 47, 131, 178, 67, 38, 238, 85, 83, 162, 226, 104, 216, 213, 227, 77, 94, 63, 197, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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