Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91bc44bad77b2f45fe7e081016fc069a55b65a7e3e52f9b9a642b5d426971561

Tx prefix hash: e869f41184b978dc55faa854134bfeec5a25d08b39181f0c9cfa159ed1c29c77
Tx public key: c4790a6a8a3ec921d5a213e4bab5d1245111a9300fd8f542caa522557ccfa277
Timestamp: 1729236564 Timestamp [UCT]: 2024-10-18 07:29:24 Age [y:d:h:m:s]: 01:025:03:41:22
Block: 1134136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276337 RingCT/type: yes/0
Extra: 01c4790a6a8a3ec921d5a213e4bab5d1245111a9300fd8f542caa522557ccfa27702110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56890c68af1674df392b46c442ee7f20d363d939d8b397bff3823953af2dfd41 0.600000000000 1617391 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": 1134146, "vin": [ { "gen": { "height": 1134136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56890c68af1674df392b46c442ee7f20d363d939d8b397bff3823953af2dfd41" } } ], "extra": [ 1, 196, 121, 10, 106, 138, 62, 201, 33, 213, 162, 19, 228, 186, 181, 209, 36, 81, 17, 169, 48, 15, 216, 245, 66, 202, 165, 34, 85, 124, 207, 162, 119, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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