Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8576e0a3ed2a837e6169b5733761084f20b22b0789290ad6906bded798137d8

Tx prefix hash: 5889b0e514715cdd7f4f979a57c8a017d11274d55b086408222d87d0128bfabc
Tx public key: 35652f15a1a3036341b0eccc5753a1e37794e138ed47e97c9f2b2c5dcc050111
Timestamp: 1712237611 Timestamp [UCT]: 2024-04-04 13:33:31 Age [y:d:h:m:s]: 01:217:07:22:28
Block: 993169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414017 RingCT/type: yes/0
Extra: 0135652f15a1a3036341b0eccc5753a1e37794e138ed47e97c9f2b2c5dcc0501110211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b013f881d97dc04d7922bd82712d64bc6fbba4f3545bbf3c3b60e068c610f585 0.600000000000 1453551 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": 993179, "vin": [ { "gen": { "height": 993169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b013f881d97dc04d7922bd82712d64bc6fbba4f3545bbf3c3b60e068c610f585" } } ], "extra": [ 1, 53, 101, 47, 21, 161, 163, 3, 99, 65, 176, 236, 204, 87, 83, 161, 227, 119, 148, 225, 56, 237, 71, 233, 124, 159, 43, 44, 93, 204, 5, 1, 17, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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