Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2896f454134c736584c1000729bf502d0ecc8e47d0af6c8c851e3cd0e24237e2

Tx prefix hash: 3f3f38039fc8d41b5815a71bc3a88b11d61dfeffef41d4882b16da93f66b70c9
Tx public key: b2d836d7c0033e85afb4a11e642db23df754465d86758a4debb5265087cfb6cc
Timestamp: 1719001514 Timestamp [UCT]: 2024-06-21 20:25:14 Age [y:d:h:m:s]: 00:354:01:55:17
Block: 1049254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253102 RingCT/type: yes/0
Extra: 01b2d836d7c0033e85afb4a11e642db23df754465d86758a4debb5265087cfb6cc02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dfd06a2a19ef5c52104edc3d88a3ed862cd22e91c88e1f499201c2a9e9d1db9 0.600000000000 1519353 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": 1049264, "vin": [ { "gen": { "height": 1049254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dfd06a2a19ef5c52104edc3d88a3ed862cd22e91c88e1f499201c2a9e9d1db9" } } ], "extra": [ 1, 178, 216, 54, 215, 192, 3, 62, 133, 175, 180, 161, 30, 100, 45, 178, 61, 247, 84, 70, 93, 134, 117, 138, 77, 235, 181, 38, 80, 135, 207, 182, 204, 2, 17, 0, 0, 0, 4, 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