Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de7a7286a0e210665052b19c78e050ae9cba58d6eab04f171a979b2e4e98267a

Tx prefix hash: 28d7b62d076359d4a874f8e1a97fdc329e6ec229a848eaf96187ba9242e2d54d
Tx public key: 738ca4e3e0710f9c66562a888fff0ac1d6311db76c45ed0c1859e1ccb08768cc
Timestamp: 1752417282 Timestamp [UCT]: 2025-07-13 14:34:42 Age [y:d:h:m:s]: 00:200:11:54:58
Block: 1324663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141945 RingCT/type: yes/0
Extra: 01738ca4e3e0710f9c66562a888fff0ac1d6311db76c45ed0c1859e1ccb08768cc021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cba81316cbfb0244572ee73aa017d4ffe958d5828c38c648352b40f522aa63d 0.600000000000 1812406 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": 1324673, "vin": [ { "gen": { "height": 1324663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cba81316cbfb0244572ee73aa017d4ffe958d5828c38c648352b40f522aa63d" } } ], "extra": [ 1, 115, 140, 164, 227, 224, 113, 15, 156, 102, 86, 42, 136, 143, 255, 10, 193, 214, 49, 29, 183, 108, 69, 237, 12, 24, 89, 225, 204, 176, 135, 104, 204, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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