Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1889f9cd0a22487f997ead1c8d127376585c17239bc4038571e0338ba84afe

Tx prefix hash: f1a9784a1547b3d44866c20163a62f406afeee7bd350e204a2317dcba26e5e2b
Tx public key: 9a1d3b822f76f484082c87f9f655c7ba1e086cf51c114f16429e7a1e117f70a9
Timestamp: 1737881557 Timestamp [UCT]: 2025-01-26 08:52:37 Age [y:d:h:m:s]: 00:143:09:51:13
Block: 1205605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102222 RingCT/type: yes/0
Extra: 019a1d3b822f76f484082c87f9f655c7ba1e086cf51c114f16429e7a1e117f70a9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 991b87eff4316c5bc5f57e2fa28dc29886acf3c3283f79cc99ea9de4524bfb0c 0.600000000000 1692302 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": 1205615, "vin": [ { "gen": { "height": 1205605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "991b87eff4316c5bc5f57e2fa28dc29886acf3c3283f79cc99ea9de4524bfb0c" } } ], "extra": [ 1, 154, 29, 59, 130, 47, 118, 244, 132, 8, 44, 135, 249, 246, 85, 199, 186, 30, 8, 108, 245, 28, 17, 79, 22, 66, 158, 122, 30, 17, 127, 112, 169, 2, 17, 0, 0, 0, 5, 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