Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ff2000f5e8d7af94c8977dbd84d1e581ac8eaa38945837ce93ed235d3dbe8a3

Tx prefix hash: a24f87ec51f1b7aae655244f96cf52924e63e7f8c32d5c19cbe3223f645e59bc
Tx public key: 4d257e2d9c5dd5ea50f70a754eb6d08d39ab759ec319fd17e79a613be9ee821d
Timestamp: 1695560600 Timestamp [UCT]: 2023-09-24 13:03:20 Age [y:d:h:m:s]: 01:126:14:02:15
Block: 855143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351522 RingCT/type: yes/0
Extra: 014d257e2d9c5dd5ea50f70a754eb6d08d39ab759ec319fd17e79a613be9ee821d0211000000034b8f5122000000000000000000

1 output(s) for total of 0.900650518000 dcy

stealth address amount amount idx
00: ee8ef55905353dafc668b8d348a599c25e629ceb3a38d0662ccf164103f21b8c 0.900650518000 1309147 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": 855153, "vin": [ { "gen": { "height": 855143 } } ], "vout": [ { "amount": 900650518, "target": { "key": "ee8ef55905353dafc668b8d348a599c25e629ceb3a38d0662ccf164103f21b8c" } } ], "extra": [ 1, 77, 37, 126, 45, 156, 93, 213, 234, 80, 247, 10, 117, 78, 182, 208, 141, 57, 171, 117, 158, 195, 25, 253, 23, 231, 154, 97, 59, 233, 238, 130, 29, 2, 17, 0, 0, 0, 3, 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