Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f490454ca7ffd41648137dd5a39fc71b52f1960a98b0db439782f89b34c2cbd

Tx prefix hash: fff925f567b9ebc22e32ad75a2aecb73ae1dfd9c733aec268fb9152081283361
Tx public key: 5fd1bd07c52b7ec36ff65f6e0e82c4e03778b75d4926dc6be01eef9bc3d8db18
Timestamp: 1712775296 Timestamp [UCT]: 2024-04-10 18:54:56 Age [y:d:h:m:s]: 01:008:00:15:42
Block: 997634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266707 RingCT/type: yes/0
Extra: 015fd1bd07c52b7ec36ff65f6e0e82c4e03778b75d4926dc6be01eef9bc3d8db180211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9554384ae50f58683c66b01b1db37a3594e3793f45e0ed837f80cfd3dfc2606d 0.600000000000 1458068 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": 997644, "vin": [ { "gen": { "height": 997634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9554384ae50f58683c66b01b1db37a3594e3793f45e0ed837f80cfd3dfc2606d" } } ], "extra": [ 1, 95, 209, 189, 7, 197, 43, 126, 195, 111, 246, 95, 110, 14, 130, 196, 224, 55, 120, 183, 93, 73, 38, 220, 107, 224, 30, 239, 155, 195, 216, 219, 24, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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