Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51a6ad21bb50ade23e15c3eee5365f0ac3ca70db7d4dd88d28469fc26ad4a1dd

Tx prefix hash: e78d683a971e61ef3f193a6bb4ed2c5ab846267fdf23d0f53306a719bbdd4c83
Tx public key: ea9c31f13dd7945281e5c1dcce4def3341b8bfd59b701707377fdc8196fa5e01
Timestamp: 1705046998 Timestamp [UCT]: 2024-01-12 08:09:58 Age [y:d:h:m:s]: 01:081:17:07:44
Block: 933570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319497 RingCT/type: yes/0
Extra: 01ea9c31f13dd7945281e5c1dcce4def3341b8bfd59b701707377fdc8196fa5e0102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7862170cbff7beac191affbd72d6d227d891304a9ec20e8a887b1d7e85e3d0a0 0.600000000000 1391536 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": 933580, "vin": [ { "gen": { "height": 933570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7862170cbff7beac191affbd72d6d227d891304a9ec20e8a887b1d7e85e3d0a0" } } ], "extra": [ 1, 234, 156, 49, 241, 61, 215, 148, 82, 129, 229, 193, 220, 206, 77, 239, 51, 65, 184, 191, 213, 155, 112, 23, 7, 55, 127, 220, 129, 150, 250, 94, 1, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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