Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9fdf70d2fc1e29d4707c5a3ab53d0729c8c1c923b7921fc81cc228b58709caa

Tx prefix hash: 9d9942855829b433ae8bbe6161242773b425166500415846db2cfc241bfdc163
Tx public key: 66f58c1dd19c17e9d74af11a5b5ad1c9c3a973bfed58c5d886a0307f8a5411be
Timestamp: 1717361058 Timestamp [UCT]: 2024-06-02 20:44:18 Age [y:d:h:m:s]: 01:159:03:24:45
Block: 1035679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372318 RingCT/type: yes/0
Extra: 0166f58c1dd19c17e9d74af11a5b5ad1c9c3a973bfed58c5d886a0307f8a5411be021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3981ee96a2e64e0493acc52b01f6234dfc9c6bd2f6be0583fbec4d9eb4656860 0.600000000000 1504202 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": 1035689, "vin": [ { "gen": { "height": 1035679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3981ee96a2e64e0493acc52b01f6234dfc9c6bd2f6be0583fbec4d9eb4656860" } } ], "extra": [ 1, 102, 245, 140, 29, 209, 156, 23, 233, 215, 74, 241, 26, 91, 90, 209, 201, 195, 169, 115, 191, 237, 88, 197, 216, 134, 160, 48, 127, 138, 84, 17, 190, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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