Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a82195023d0b9c3d72d4ca60fdc4afeee00ce49e8150f81e3a78db8ab809a7f1

Tx prefix hash: ddf8b266c3823bb6afd77a2609e8829a8f42b8b1c7372c988df0062dd988d37a
Tx public key: dd21ecbc75caee3af48ea4afa03dff2f230dd716d7db56a50c2569a416afc069
Timestamp: 1737300359 Timestamp [UCT]: 2025-01-19 15:25:59 Age [y:d:h:m:s]: 00:151:00:50:56
Block: 1200792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107682 RingCT/type: yes/0
Extra: 01dd21ecbc75caee3af48ea4afa03dff2f230dd716d7db56a50c2569a416afc069021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23a15ae39a5d6fa5ea7f30bf5e35d9025c2a5aed1a34db9c629644a80b7ec343 0.600000000000 1687439 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": 1200802, "vin": [ { "gen": { "height": 1200792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23a15ae39a5d6fa5ea7f30bf5e35d9025c2a5aed1a34db9c629644a80b7ec343" } } ], "extra": [ 1, 221, 33, 236, 188, 117, 202, 238, 58, 244, 142, 164, 175, 160, 61, 255, 47, 35, 13, 215, 22, 215, 219, 86, 165, 12, 37, 105, 164, 22, 175, 192, 105, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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