Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c44dd5a65b405adaa4a40022f922531651bc22b3fd880fb5e805f73aaf1eafe3

Tx prefix hash: 70d9b09df18bbd63ce6cf457e7f431ce535592b5bc3ff23db699e2c78acba1b6
Tx public key: 688a9bb305d2ff7e0be5d34521f92455bdc3eb2a4c8f058fce7b663bf877ed3c
Timestamp: 1607617073 Timestamp [UCT]: 2020-12-10 16:17:53 Age [y:d:h:m:s]: 04:015:12:39:15
Block: 159603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1023047 RingCT/type: yes/0
Extra: 01688a9bb305d2ff7e0be5d34521f92455bdc3eb2a4c8f058fce7b663bf877ed3c02110000017827e2517e000000000000000000

1 output(s) for total of 181.625656016000 dcy

stealth address amount amount idx
00: fb0504f06babd924a8bc17dbbfa41efc92881e4f749d51b7e4b9f9d1d5fb1db9 181.625656016000 279438 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": 159613, "vin": [ { "gen": { "height": 159603 } } ], "vout": [ { "amount": 181625656016, "target": { "key": "fb0504f06babd924a8bc17dbbfa41efc92881e4f749d51b7e4b9f9d1d5fb1db9" } } ], "extra": [ 1, 104, 138, 155, 179, 5, 210, 255, 126, 11, 229, 211, 69, 33, 249, 36, 85, 189, 195, 235, 42, 76, 143, 5, 143, 206, 123, 102, 59, 248, 119, 237, 60, 2, 17, 0, 0, 1, 120, 39, 226, 81, 126, 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