Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9ca70599a0df158d4b3c86b26637791ba23870c8623799f2a1e4bb5abfa617

Tx prefix hash: 6ee913dcf173ee5788dd9c7a436caae56b331508c88524f87cbbac2566eaeb6e
Tx public key: 403517b8cc77afdf6ed57b2c0fc09f794428974ef09188952ecfc4f4c15c41ff
Timestamp: 1583745596 Timestamp [UCT]: 2020-03-09 09:19:56 Age [y:d:h:m:s]: 04:251:13:18:05
Block: 78904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074928 RingCT/type: yes/0
Extra: 01403517b8cc77afdf6ed57b2c0fc09f794428974ef09188952ecfc4f4c15c41ff0211000000154ac5aa02000000000000000000

1 output(s) for total of 336.170101243000 dcy

stealth address amount amount idx
00: 8beaa704197493fe753af4f9d888c47e3f533b732843db3a1a6f81af4487caf5 336.170101243000 144578 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": 78914, "vin": [ { "gen": { "height": 78904 } } ], "vout": [ { "amount": 336170101243, "target": { "key": "8beaa704197493fe753af4f9d888c47e3f533b732843db3a1a6f81af4487caf5" } } ], "extra": [ 1, 64, 53, 23, 184, 204, 119, 175, 223, 110, 213, 123, 44, 15, 192, 159, 121, 68, 40, 151, 78, 240, 145, 136, 149, 46, 207, 196, 244, 193, 92, 65, 255, 2, 17, 0, 0, 0, 21, 74, 197, 170, 2, 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