Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7ae7166d5b35840a5576875f27c0e3e72d404e22bd7f1b4cda9e954c7892fa6

Tx prefix hash: 30b7f84e06bb5742d14c1f6a374034bcaef6571d7a3d5713498c6655c11c07a7
Tx public key: 0b68d9d7386666015f4083a03df142300fb3077ffaa3d1dcc47fec20fe859a15
Timestamp: 1721060219 Timestamp [UCT]: 2024-07-15 16:16:59 Age [y:d:h:m:s]: 00:264:01:09:19
Block: 1066365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188624 RingCT/type: yes/0
Extra: 010b68d9d7386666015f4083a03df142300fb3077ffaa3d1dcc47fec20fe859a15021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa2d7e54bc027fb943e7ef0e66c100d2db96bc6de2715be3b3c45eceb8b75d1c 0.600000000000 1536938 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": 1066375, "vin": [ { "gen": { "height": 1066365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2d7e54bc027fb943e7ef0e66c100d2db96bc6de2715be3b3c45eceb8b75d1c" } } ], "extra": [ 1, 11, 104, 217, 215, 56, 102, 102, 1, 95, 64, 131, 160, 61, 241, 66, 48, 15, 179, 7, 127, 250, 163, 209, 220, 196, 127, 236, 32, 254, 133, 154, 21, 2, 17, 0, 0, 0, 6, 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