Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8516d82e6d8e865b51db4ecf961de842455be30df063e0e205944a3a40b8df84

Tx prefix hash: e5ddb837eb32830662bf56116ca793a102eae5ef7fa271b4ae60296e1351ebb5
Tx public key: aa972ed4ee68e8f8045a77c86700b118354a11c0ec958d3d6b9217519e6eea42
Timestamp: 1725268917 Timestamp [UCT]: 2024-09-02 09:21:57 Age [y:d:h:m:s]: 00:209:16:42:12
Block: 1101238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149707 RingCT/type: yes/0
Extra: 01aa972ed4ee68e8f8045a77c86700b118354a11c0ec958d3d6b9217519e6eea42021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 584cb2037068c3381ffb19ab07a0bb77d02bd6e4be0ad04d36f5c674da332043 0.600000000000 1577223 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": 1101248, "vin": [ { "gen": { "height": 1101238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "584cb2037068c3381ffb19ab07a0bb77d02bd6e4be0ad04d36f5c674da332043" } } ], "extra": [ 1, 170, 151, 46, 212, 238, 104, 232, 248, 4, 90, 119, 200, 103, 0, 177, 24, 53, 74, 17, 192, 236, 149, 141, 61, 107, 146, 23, 81, 158, 110, 234, 66, 2, 17, 0, 0, 0, 6, 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