Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977442ae03ce39c5c0acb2f79a41786c39c90e038a10efac2c8d15b2ea34313e

Tx prefix hash: 9dffea68ef578d47b8ee9830bd611ce42ed1c41fceec4d89f7440c354d930983
Tx public key: 495ff1bebae3a3ccc5caf24c1f10fe93cc38ee444c7d96f6ca6a0958a2ebc18b
Timestamp: 1736944986 Timestamp [UCT]: 2025-01-15 12:43:06 Age [y:d:h:m:s]: 00:152:23:49:53
Block: 1197890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109066 RingCT/type: yes/0
Extra: 01495ff1bebae3a3ccc5caf24c1f10fe93cc38ee444c7d96f6ca6a0958a2ebc18b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9893f567e3622eb04bceca688001060cc5b9af989c04a1db4af72d3c2ebe4fb0 0.600000000000 1684507 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": 1197900, "vin": [ { "gen": { "height": 1197890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9893f567e3622eb04bceca688001060cc5b9af989c04a1db4af72d3c2ebe4fb0" } } ], "extra": [ 1, 73, 95, 241, 190, 186, 227, 163, 204, 197, 202, 242, 76, 31, 16, 254, 147, 204, 56, 238, 68, 76, 125, 150, 246, 202, 106, 9, 88, 162, 235, 193, 139, 2, 17, 0, 0, 0, 2, 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