Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51c523366659fafb666054b649fb89c565102ef6f13e871f4a9683c08b4abb81

Tx prefix hash: aeea6b4004bb0028f55a7913d4aa8df5f1e878e6437f0d2a3ae33954a9f91186
Tx public key: 67aa573d5c99cd52f8a308cc8974779b5d902867b4098ee5279a96e32ae2fcde
Timestamp: 1733614732 Timestamp [UCT]: 2024-12-07 23:38:52 Age [y:d:h:m:s]: 00:335:08:18:48
Block: 1170330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237185 RingCT/type: yes/0
Extra: 0167aa573d5c99cd52f8a308cc8974779b5d902867b4098ee5279a96e32ae2fcde021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29f9ef18fdf51159f1b6e2d5354995b50e03b388a64ee312434791100f7f2972 0.600000000000 1656059 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": 1170340, "vin": [ { "gen": { "height": 1170330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f9ef18fdf51159f1b6e2d5354995b50e03b388a64ee312434791100f7f2972" } } ], "extra": [ 1, 103, 170, 87, 61, 92, 153, 205, 82, 248, 163, 8, 204, 137, 116, 119, 155, 93, 144, 40, 103, 180, 9, 142, 229, 39, 154, 150, 227, 42, 226, 252, 222, 2, 17, 0, 0, 0, 6, 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