Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df024f69809af3c51bd3b0b94591de45a1c514dd677ab0570f1c0ddfc992f79b

Tx prefix hash: 826c97b6780b4a3ac85c4bb6d44b122d3bfd2915db1d8c1d42f45fa505968ea8
Tx public key: 4287bbaeca0150da0c5c73227c6e0c18f248bcb5934a1a76efb837dcf94f8ddb
Timestamp: 1720758817 Timestamp [UCT]: 2024-07-12 04:33:37 Age [y:d:h:m:s]: 00:338:23:10:39
Block: 1063854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242128 RingCT/type: yes/0
Extra: 014287bbaeca0150da0c5c73227c6e0c18f248bcb5934a1a76efb837dcf94f8ddb02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01dbcebb9aa145cc962c238498b37817b63039c9153e9eac7eb8a737a40a6485 0.600000000000 1534371 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": 1063864, "vin": [ { "gen": { "height": 1063854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01dbcebb9aa145cc962c238498b37817b63039c9153e9eac7eb8a737a40a6485" } } ], "extra": [ 1, 66, 135, 187, 174, 202, 1, 80, 218, 12, 92, 115, 34, 124, 110, 12, 24, 242, 72, 188, 181, 147, 74, 26, 118, 239, 184, 55, 220, 249, 79, 141, 219, 2, 17, 0, 0, 0, 8, 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