Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5420224271f144d2182aafc1ca4b4e20eadcaac3975a93bdcc301671dc3fb609

Tx prefix hash: 2bbb7a1af55c5860d9e075f692b8c6b22052aa250d1a7f911371b5f04ecdbe1f
Tx public key: d5898d3982b917afe96475293b6c55c350c7f2387053302b842dfa0aca30c9b7
Timestamp: 1745965077 Timestamp [UCT]: 2025-04-29 22:17:57 Age [y:d:h:m:s]: 00:194:19:17:00
Block: 1272304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136925 RingCT/type: yes/0
Extra: 01d5898d3982b917afe96475293b6c55c350c7f2387053302b842dfa0aca30c9b702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a3a5d6fa5d7c37e38f6f5d0d0563fe8ae1b26dd46055050070ffdb1ff93050 0.600000000000 1759577 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": 1272314, "vin": [ { "gen": { "height": 1272304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a3a5d6fa5d7c37e38f6f5d0d0563fe8ae1b26dd46055050070ffdb1ff93050" } } ], "extra": [ 1, 213, 137, 141, 57, 130, 185, 23, 175, 233, 100, 117, 41, 59, 108, 85, 195, 80, 199, 242, 56, 112, 83, 48, 43, 132, 45, 250, 10, 202, 48, 201, 183, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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