Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d52a09ae1740a45d38a382956793b1bcb1c5b77853d685639ab5af2e7e000ab2

Tx prefix hash: f310fdd2289bc1a051d943dbf5bebf950ed0d082b963205c90ff17d1036ed0e2
Tx public key: 7af8e2a14da67ba8c45cf831bea6d5b6ffeb5f542b7f0a5c221a08bc0b88b1e2
Timestamp: 1713303667 Timestamp [UCT]: 2024-04-16 21:41:07 Age [y:d:h:m:s]: 01:202:18:43:30
Block: 1002023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403581 RingCT/type: yes/0
Extra: 017af8e2a14da67ba8c45cf831bea6d5b6ffeb5f542b7f0a5c221a08bc0b88b1e202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b1af4cd7289c88cffc866249e5b189aa9764c5e42bde6f02e0d907f69badd13 0.600000000000 1462537 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": 1002033, "vin": [ { "gen": { "height": 1002023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b1af4cd7289c88cffc866249e5b189aa9764c5e42bde6f02e0d907f69badd13" } } ], "extra": [ 1, 122, 248, 226, 161, 77, 166, 123, 168, 196, 92, 248, 49, 190, 166, 213, 182, 255, 235, 95, 84, 43, 127, 10, 92, 34, 26, 8, 188, 11, 136, 177, 226, 2, 17, 0, 0, 0, 3, 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