Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401478d548c53aefed6e7f7b672fd221cb27cc3c9ae6c34a65c9ab7c6e286545

Tx prefix hash: 48b6ad1d6e0ef91888bb4e2f6ca7293a186b1ce0bd58c5e36fe326ff03b9dc35
Tx public key: 0298676d954c83618c795a6bb0af525f79bd8e276c09863525a82e9fa33ef764
Timestamp: 1727799898 Timestamp [UCT]: 2024-10-01 16:24:58 Age [y:d:h:m:s]: 01:049:12:39:36
Block: 1122224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293800 RingCT/type: yes/0
Extra: 010298676d954c83618c795a6bb0af525f79bd8e276c09863525a82e9fa33ef76402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d616efab4a63bf9999aad646705c0fd109a35ab3f04d15f952fff6f42408271 0.600000000000 1604631 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": 1122234, "vin": [ { "gen": { "height": 1122224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d616efab4a63bf9999aad646705c0fd109a35ab3f04d15f952fff6f42408271" } } ], "extra": [ 1, 2, 152, 103, 109, 149, 76, 131, 97, 140, 121, 90, 107, 176, 175, 82, 95, 121, 189, 142, 39, 108, 9, 134, 53, 37, 168, 46, 159, 163, 62, 247, 100, 2, 17, 0, 0, 0, 7, 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