Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99848d5675fe7db3150b23ee5f11ec1e93cbe5b3cb247d016f722ad60336e287

Tx prefix hash: a736e0ecd71fa0583b530c3f02a5a800072e73d6b9d88d3b96c3965609744ed8
Tx public key: d196fb87c4234642be455a70a49277b16655f38d795a5f3d1605e072b6a05599
Timestamp: 1749433512 Timestamp [UCT]: 2025-06-09 01:45:12 Age [y:d:h:m:s]: 00:164:06:16:17
Block: 1301033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115074 RingCT/type: yes/0
Extra: 01d196fb87c4234642be455a70a49277b16655f38d795a5f3d1605e072b6a055990211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 734c029e6ec2d2390cb764340c745256e1b2068a4e928ccdc0de936b040e1c8d 0.600000000000 1788586 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": 1301043, "vin": [ { "gen": { "height": 1301033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "734c029e6ec2d2390cb764340c745256e1b2068a4e928ccdc0de936b040e1c8d" } } ], "extra": [ 1, 209, 150, 251, 135, 196, 35, 70, 66, 190, 69, 90, 112, 164, 146, 119, 177, 102, 85, 243, 141, 121, 90, 95, 61, 22, 5, 224, 114, 182, 160, 85, 153, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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