Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a340837fd2c680420311c543a2a2aa6ce602f8034a69c92336b431f56989de3

Tx prefix hash: 73730f68a52c0868dca0965f199606b04744783586db54f4067765b6a6c38fd3
Tx public key: 363276bc186e2d841b6c775a6aac2f2618e60b7538cd6d09fc497cc25c33f801
Timestamp: 1707495783 Timestamp [UCT]: 2024-02-09 16:23:03 Age [y:d:h:m:s]: 01:068:13:23:50
Block: 953878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310059 RingCT/type: yes/0
Extra: 01363276bc186e2d841b6c775a6aac2f2618e60b7538cd6d09fc497cc25c33f8010211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 098793ea3bfa946b79158f65f7de0d55f5f3de36a00a849e9e36f9dfb8c43007 0.600000000000 1413148 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": 953888, "vin": [ { "gen": { "height": 953878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "098793ea3bfa946b79158f65f7de0d55f5f3de36a00a849e9e36f9dfb8c43007" } } ], "extra": [ 1, 54, 50, 118, 188, 24, 110, 45, 132, 27, 108, 119, 90, 106, 172, 47, 38, 24, 230, 11, 117, 56, 205, 109, 9, 252, 73, 124, 194, 92, 51, 248, 1, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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