Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8230d10f26f44041755c29032b32502a8e44e4ed0fe7348a30df1c833524c1f

Tx prefix hash: 7d05884c936488a35b4080ed970b780826aa305eadf7d5401130248279e764d0
Tx public key: 4d94c9e9fa9fd755522949a666a7ca56fe4c0f0d0b97f19c708d86f17851bcee
Timestamp: 1709605118 Timestamp [UCT]: 2024-03-05 02:18:38 Age [y:d:h:m:s]: 01:071:13:25:13
Block: 971384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312166 RingCT/type: yes/0
Extra: 014d94c9e9fa9fd755522949a666a7ca56fe4c0f0d0b97f19c708d86f17851bcee02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f25401e5e504031f977562ac62ad73cf3e63490b495410c49e8845b9d087b6b6 0.600000000000 1431279 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": 971394, "vin": [ { "gen": { "height": 971384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f25401e5e504031f977562ac62ad73cf3e63490b495410c49e8845b9d087b6b6" } } ], "extra": [ 1, 77, 148, 201, 233, 250, 159, 215, 85, 82, 41, 73, 166, 102, 167, 202, 86, 254, 76, 15, 13, 11, 151, 241, 156, 112, 141, 134, 241, 120, 81, 188, 238, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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