Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 560fb4acb04724d7817f063339fa215d247af4cba7a058d9164ebcb732ee7a63

Tx prefix hash: 884ea3a0b2d521fcf9b54914b21b3cb6131593aef92ac216a3b8e0cb0db7204a
Tx public key: eebda9703a760c9bf8347df006df7ae816a3ec29b6cb7f941579d681cef2e287
Timestamp: 1764225723 Timestamp [UCT]: 2025-11-27 06:42:03 Age [y:d:h:m:s]: 00:026:09:41:08
Block: 1421085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18886 RingCT/type: yes/0
Extra: 01eebda9703a760c9bf8347df006df7ae816a3ec29b6cb7f941579d681cef2e2870211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3b048db12f712894e59fbd37aa868914df08a79bc0cc4d747e489e3d0b0061e 0.600000000000 1909640 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": 1421095, "vin": [ { "gen": { "height": 1421085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3b048db12f712894e59fbd37aa868914df08a79bc0cc4d747e489e3d0b0061e" } } ], "extra": [ 1, 238, 189, 169, 112, 58, 118, 12, 155, 248, 52, 125, 240, 6, 223, 122, 232, 22, 163, 236, 41, 182, 203, 127, 148, 21, 121, 214, 129, 206, 242, 226, 135, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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