Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89db51614c11e3f91d75489418244d8644ea0e8fccd53d3ec26efcb20670970b

Tx prefix hash: 341316b89895f0e92b55495c590e7a930696dfdd3d97d62456bb30634acedc5e
Tx public key: c6f72f2272065e69919ed2216c8246a5913dcd4b7a9a2f20f1bfe2e01c050b9b
Timestamp: 1737764429 Timestamp [UCT]: 2025-01-25 00:20:29 Age [y:d:h:m:s]: 00:299:07:41:00
Block: 1204634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211471 RingCT/type: yes/0
Extra: 01c6f72f2272065e69919ed2216c8246a5913dcd4b7a9a2f20f1bfe2e01c050b9b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 975c0aab0fe39271977dbea784a5ee9b26e22e3ab2d4c50aa74354ecae2aac1c 0.600000000000 1691325 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": 1204644, "vin": [ { "gen": { "height": 1204634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "975c0aab0fe39271977dbea784a5ee9b26e22e3ab2d4c50aa74354ecae2aac1c" } } ], "extra": [ 1, 198, 247, 47, 34, 114, 6, 94, 105, 145, 158, 210, 33, 108, 130, 70, 165, 145, 61, 205, 75, 122, 154, 47, 32, 241, 191, 226, 224, 28, 5, 11, 155, 2, 17, 0, 0, 0, 1, 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