Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2160e107a5b609777d4e40b985eb7f4dd97ea9ce5e58bc9bcb12139a03f596fb

Tx prefix hash: 73bf4e011e1b1c36cfba809ef9e1ec78de5815c12a13b2c3421a4a3cec098ed8
Tx public key: c6016a7f2500f12ecd7e05e91069b117f6b527b533e9587ff9393d6caa16f62f
Timestamp: 1693427858 Timestamp [UCT]: 2023-08-30 20:37:38 Age [y:d:h:m:s]: 01:140:23:17:56
Block: 837438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362100 RingCT/type: yes/0
Extra: 01c6016a7f2500f12ecd7e05e91069b117f6b527b533e9587ff9393d6caa16f62f0211000000024b8f5122000000000000000000

1 output(s) for total of 1.030909031000 dcy

stealth address amount amount idx
00: f0a17ea1d43980dd606b91d4da1564585fd791ea8ef7ae0ac3d3cbf4c150f391 1.030909031000 1290066 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": 837448, "vin": [ { "gen": { "height": 837438 } } ], "vout": [ { "amount": 1030909031, "target": { "key": "f0a17ea1d43980dd606b91d4da1564585fd791ea8ef7ae0ac3d3cbf4c150f391" } } ], "extra": [ 1, 198, 1, 106, 127, 37, 0, 241, 46, 205, 126, 5, 233, 16, 105, 177, 23, 246, 181, 39, 181, 51, 233, 88, 127, 249, 57, 61, 108, 170, 22, 246, 47, 2, 17, 0, 0, 0, 2, 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