Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18fd9f44f66351c408710da1022f10b8d93cb8c15cc5a1c006c4be3d5c191cec

Tx prefix hash: 81f89a803cf609c5ec6b359c07349d3d3f45c96596cc40d4d7d0bd30771984d3
Tx public key: 6ff27b79aed394c489baf42fba9f209a224216fba8846720cfa64419af1e5841
Timestamp: 1716117426 Timestamp [UCT]: 2024-05-19 11:17:06 Age [y:d:h:m:s]: 00:238:02:32:30
Block: 1025376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170404 RingCT/type: yes/0
Extra: 016ff27b79aed394c489baf42fba9f209a224216fba8846720cfa64419af1e584102110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 842e11c6675a2aa8adb234f1372ac8e27aeae8ae1485650bf628e692dde4a0ea 0.600000000000 1491833 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": 1025386, "vin": [ { "gen": { "height": 1025376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "842e11c6675a2aa8adb234f1372ac8e27aeae8ae1485650bf628e692dde4a0ea" } } ], "extra": [ 1, 111, 242, 123, 121, 174, 211, 148, 196, 137, 186, 244, 47, 186, 159, 32, 154, 34, 66, 22, 251, 168, 132, 103, 32, 207, 166, 68, 25, 175, 30, 88, 65, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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