Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d1aada2c4b5694531647c559a2ffc328e2de59cc4fefe81e47d3da17213c09

Tx prefix hash: 331d86d35981a22def54304bb5226b38d82d16d7b207264f56463a236394c177
Tx public key: 78fc5aa24a0b1549251bc2a74a74da9a0f9758e4c8f3ccad24fa7a0a52800559
Timestamp: 1723333629 Timestamp [UCT]: 2024-08-10 23:47:09 Age [y:d:h:m:s]: 00:249:17:45:26
Block: 1085194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178373 RingCT/type: yes/0
Extra: 0178fc5aa24a0b1549251bc2a74a74da9a0f9758e4c8f3ccad24fa7a0a52800559021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 783690d3016c4550fbc3e967bc4acc9f4506626f83f82d1c7ffad8cfd0edc6a4 0.600000000000 1559723 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": 1085204, "vin": [ { "gen": { "height": 1085194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "783690d3016c4550fbc3e967bc4acc9f4506626f83f82d1c7ffad8cfd0edc6a4" } } ], "extra": [ 1, 120, 252, 90, 162, 74, 11, 21, 73, 37, 27, 194, 167, 74, 116, 218, 154, 15, 151, 88, 228, 200, 243, 204, 173, 36, 250, 122, 10, 82, 128, 5, 89, 2, 17, 0, 0, 0, 4, 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