Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a3852909ef1c6fe4a813627bef688c6c155c73f8af4f96c9cd65c9d52c7139b

Tx prefix hash: e5268d80c4b23f40519706de27962271212a5b31484858fb16570a0a4e568c60
Tx public key: 6b9ae452d002fee08c7c5d60f623e35dc36d3d9f0513cd79ea98221ebf9f9100
Timestamp: 1725372612 Timestamp [UCT]: 2024-09-03 14:10:12 Age [y:d:h:m:s]: 01:109:22:49:39
Block: 1102105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337064 RingCT/type: yes/0
Extra: 016b9ae452d002fee08c7c5d60f623e35dc36d3d9f0513cd79ea98221ebf9f9100021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05b3fd33e75326b0a4a8e91691d0a06d0f82fa61b2e6f9b90493b1cc81710617 0.600000000000 1578408 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": 1102115, "vin": [ { "gen": { "height": 1102105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05b3fd33e75326b0a4a8e91691d0a06d0f82fa61b2e6f9b90493b1cc81710617" } } ], "extra": [ 1, 107, 154, 228, 82, 208, 2, 254, 224, 140, 124, 93, 96, 246, 35, 227, 93, 195, 109, 61, 159, 5, 19, 205, 121, 234, 152, 34, 30, 191, 159, 145, 0, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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