Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4ab15c564491f9a8aa6aef7fdf241a83cf114bdfac1ece53de944a69461f0b

Tx prefix hash: 27876885a87d59569f474bcecd9f6b4f9dad6b912173cb39026f767b69a255f5
Tx public key: 3c6af4e396491c3796aa2ce3d2b6589a60111156b9916ac24e855e2e8184768e
Timestamp: 1720793701 Timestamp [UCT]: 2024-07-12 14:15:01 Age [y:d:h:m:s]: 00:246:01:44:13
Block: 1064149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175794 RingCT/type: yes/0
Extra: 013c6af4e396491c3796aa2ce3d2b6589a60111156b9916ac24e855e2e8184768e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c935a9ee64e85ab940afb775c72eba4b46e9bcb64fc2a1f13bc2ea4ec8a365 0.600000000000 1534672 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": 1064159, "vin": [ { "gen": { "height": 1064149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c935a9ee64e85ab940afb775c72eba4b46e9bcb64fc2a1f13bc2ea4ec8a365" } } ], "extra": [ 1, 60, 106, 244, 227, 150, 73, 28, 55, 150, 170, 44, 227, 210, 182, 88, 154, 96, 17, 17, 86, 185, 145, 106, 194, 78, 133, 94, 46, 129, 132, 118, 142, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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