Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb75861aea431f47a673248adf46d9b41d07cb10e7e825a9764543bfb95e21f

Tx prefix hash: 360a94a3026971aab405e8522672b7a131264c318106ff0a60fcdef659f0ef6b
Tx public key: 6d309b8b7e446c240213de605683b341d07c6c721a4afd8d68f0083bfb71517e
Timestamp: 1739869815 Timestamp [UCT]: 2025-02-18 09:10:15 Age [y:d:h:m:s]: 00:267:02:00:31
Block: 1221808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188665 RingCT/type: yes/0
Extra: 016d309b8b7e446c240213de605683b341d07c6c721a4afd8d68f0083bfb71517e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf0ad6ab1fe6e4604926449b26f31028041f46da261bbe4d9fd6a6277128d8a9 0.600000000000 1708655 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": 1221818, "vin": [ { "gen": { "height": 1221808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf0ad6ab1fe6e4604926449b26f31028041f46da261bbe4d9fd6a6277128d8a9" } } ], "extra": [ 1, 109, 48, 155, 139, 126, 68, 108, 36, 2, 19, 222, 96, 86, 131, 179, 65, 208, 124, 108, 114, 26, 74, 253, 141, 104, 240, 8, 59, 251, 113, 81, 126, 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