Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96e3b15e21a6a2d60b388a6fd1dff9a4b7a5d0c728ba332c3bddb00e724233ee

Tx prefix hash: d24305539740be0d2ac6d5d0db550218389e9625cdaaa94a63aab10e4eb3fa3e
Tx public key: 2a6a7bf27dec71e4e82ce3426650a5bcaa15d169638d40e6cddcc97e4ba61025
Timestamp: 1725305521 Timestamp [UCT]: 2024-09-02 19:32:01 Age [y:d:h:m:s]: 00:214:13:46:01
Block: 1101538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153209 RingCT/type: yes/0
Extra: 012a6a7bf27dec71e4e82ce3426650a5bcaa15d169638d40e6cddcc97e4ba61025021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a237cb1fabb24d57586d8bb3ad95d74343cdb75b32c98a84d9013b2793ed266c 0.600000000000 1577629 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": 1101548, "vin": [ { "gen": { "height": 1101538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a237cb1fabb24d57586d8bb3ad95d74343cdb75b32c98a84d9013b2793ed266c" } } ], "extra": [ 1, 42, 106, 123, 242, 125, 236, 113, 228, 232, 44, 227, 66, 102, 80, 165, 188, 170, 21, 209, 105, 99, 141, 64, 230, 205, 220, 201, 126, 75, 166, 16, 37, 2, 17, 0, 0, 0, 1, 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