Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6430977fa0350419cd6906aa1d928a637da33fe703189bae3b69597dd7085ee7

Tx prefix hash: 1c24a9c681e88f42e0a7a7b171cc09680c45466b5b22f55eebbf480ca05726ac
Tx public key: 9ce906b7f22cff625dbd3453a95a821d6d9df80072089c2b5e7a1d9502431bab
Timestamp: 1696485634 Timestamp [UCT]: 2023-10-05 06:00:34 Age [y:d:h:m:s]: 01:188:12:10:02
Block: 862812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395772 RingCT/type: yes/0
Extra: 019ce906b7f22cff625dbd3453a95a821d6d9df80072089c2b5e7a1d9502431bab02110000000833af99f4000000000000000000

1 output(s) for total of 0.849465434000 dcy

stealth address amount amount idx
00: 621ee4eb652b2e93b10036119e9259d06fede88e14771f9c71c129d5624f1776 0.849465434000 1317250 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": 862822, "vin": [ { "gen": { "height": 862812 } } ], "vout": [ { "amount": 849465434, "target": { "key": "621ee4eb652b2e93b10036119e9259d06fede88e14771f9c71c129d5624f1776" } } ], "extra": [ 1, 156, 233, 6, 183, 242, 44, 255, 98, 93, 189, 52, 83, 169, 90, 130, 29, 109, 157, 248, 0, 114, 8, 156, 43, 94, 122, 29, 149, 2, 67, 27, 171, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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