Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f572998185e779516ba7827aa796ab8d251741a578db77e216e04bea4cf0993

Tx prefix hash: 9fc5941bbedddfe9d7046c8ca6ed694e58465082413cefcf629376b630c2e0c8
Tx public key: b9e9904318bedd1bcc5c694a1db4cee87cde8e962f1c83c0123618e7d42373e6
Timestamp: 1706312674 Timestamp [UCT]: 2024-01-26 23:44:34 Age [y:d:h:m:s]: 01:143:16:19:39
Block: 944052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363709 RingCT/type: yes/0
Extra: 01b9e9904318bedd1bcc5c694a1db4cee87cde8e962f1c83c0123618e7d42373e602110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa4bcf59520e015bf9642276014bc6cc9279c649293c2c589176387dae20b27d 0.600000000000 1402278 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": 944062, "vin": [ { "gen": { "height": 944052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa4bcf59520e015bf9642276014bc6cc9279c649293c2c589176387dae20b27d" } } ], "extra": [ 1, 185, 233, 144, 67, 24, 190, 221, 27, 204, 92, 105, 74, 29, 180, 206, 232, 124, 222, 142, 150, 47, 28, 131, 192, 18, 54, 24, 231, 212, 35, 115, 230, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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