Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd23ea09aa7d137f9505571a5de8329fcd98e93aaf714e30bc16beec5d21c91c

Tx prefix hash: 705565e8142b8b995faaf76290cd10a984a0db14e89a9dbeac314beb459dc38b
Tx public key: eb8428488a8511214c7634a653db0fa10dc3e7b72bce73b8e7c410d68cefe5e4
Timestamp: 1702075337 Timestamp [UCT]: 2023-12-08 22:42:17 Age [y:d:h:m:s]: 01:332:19:08:24
Block: 908945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496707 RingCT/type: yes/0
Extra: 01eb8428488a8511214c7634a653db0fa10dc3e7b72bce73b8e7c410d68cefe5e402110000001ee6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af29ee1f6ebc901d90048df0cbd279b24792e7a244352c7ec74442a5056b6d66 0.600000000000 1366008 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": 908955, "vin": [ { "gen": { "height": 908945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af29ee1f6ebc901d90048df0cbd279b24792e7a244352c7ec74442a5056b6d66" } } ], "extra": [ 1, 235, 132, 40, 72, 138, 133, 17, 33, 76, 118, 52, 166, 83, 219, 15, 161, 13, 195, 231, 183, 43, 206, 115, 184, 231, 196, 16, 214, 140, 239, 229, 228, 2, 17, 0, 0, 0, 30, 230, 210, 127, 156, 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