Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ab652db0c19d5bb9513b59250f1c0304445cc0678bdd80386b8ef02da8e56d6

Tx prefix hash: b6524562b928a158172e1f05eb1b13a4567a2ad174101a59e228c8a23fb060fa
Tx public key: 95233e30991d2fac35ab7a17361857e3106ea36f74c0d8f42d7b97c79f410c4a
Timestamp: 1721998282 Timestamp [UCT]: 2024-07-26 12:51:22 Age [y:d:h:m:s]: 00:313:08:47:56
Block: 1074124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223922 RingCT/type: yes/0
Extra: 0195233e30991d2fac35ab7a17361857e3106ea36f74c0d8f42d7b97c79f410c4a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c33031f1ac98622c5c23b9fe4dcf8c35226e05b29417485c567894f418abdb43 0.600000000000 1546637 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": 1074134, "vin": [ { "gen": { "height": 1074124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c33031f1ac98622c5c23b9fe4dcf8c35226e05b29417485c567894f418abdb43" } } ], "extra": [ 1, 149, 35, 62, 48, 153, 29, 47, 172, 53, 171, 122, 23, 54, 24, 87, 227, 16, 110, 163, 111, 116, 192, 216, 244, 45, 123, 151, 199, 159, 65, 12, 74, 2, 17, 0, 0, 0, 5, 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