Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ba365064b2e77351259c36b2901af53a4fbb1916f7d4808f49df5244fdc0b9

Tx prefix hash: ee8d8d39ed3234f436662dbb90dd120a1b41778b8d3c0d91d041ac4ff6caf652
Tx public key: ac3244a30c25817a681cb3520136707168ddfc219e9c2760d2799e7700a24ab5
Timestamp: 1700758923 Timestamp [UCT]: 2023-11-23 17:02:03 Age [y:d:h:m:s]: 01:172:07:03:52
Block: 898038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384332 RingCT/type: yes/0
Extra: 01ac3244a30c25817a681cb3520136707168ddfc219e9c2760d2799e7700a24ab50211000000014b8f5122000000000000000000

1 output(s) for total of 0.649272934000 dcy

stealth address amount amount idx
00: 5e827cf9c6d5d9094ab3571d7a04a76fba62868d6c80acd43f49181c4f76bfd4 0.649272934000 1354441 of 0

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": 898048, "vin": [ { "gen": { "height": 898038 } } ], "vout": [ { "amount": 649272934, "target": { "key": "5e827cf9c6d5d9094ab3571d7a04a76fba62868d6c80acd43f49181c4f76bfd4" } } ], "extra": [ 1, 172, 50, 68, 163, 12, 37, 129, 122, 104, 28, 179, 82, 1, 54, 112, 113, 104, 221, 252, 33, 158, 156, 39, 96, 210, 121, 158, 119, 0, 162, 74, 181, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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