Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6190f2cc135bfdfbd91b23c562223e73907dd8c3a5f19c598110e5b74884170e

Tx prefix hash: 08bc7b34164c0cfe5da158b5e31b6379ca8bcb741d67c30a72dc3c94e8d99927
Tx public key: 51b9004d3d90a301816906fd3f8da7ff312d5527f2d0e965c93dde42098d2435
Timestamp: 1732438537 Timestamp [UCT]: 2024-11-24 08:55:37 Age [y:d:h:m:s]: 00:130:17:49:10
Block: 1160577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93244 RingCT/type: yes/0
Extra: 0151b9004d3d90a301816906fd3f8da7ff312d5527f2d0e965c93dde42098d2435021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a781b1c5b84ea999d9aadef20b6f7fdf1aae1125442e17db821125a06acd383 0.600000000000 1646224 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": 1160587, "vin": [ { "gen": { "height": 1160577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a781b1c5b84ea999d9aadef20b6f7fdf1aae1125442e17db821125a06acd383" } } ], "extra": [ 1, 81, 185, 0, 77, 61, 144, 163, 1, 129, 105, 6, 253, 63, 141, 167, 255, 49, 45, 85, 39, 242, 208, 233, 101, 201, 61, 222, 66, 9, 141, 36, 53, 2, 17, 0, 0, 0, 3, 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