Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d24acfb62913be1c142eb4d80d6fe7d4f35f8d0fdefdba8dd38fc23a7e4cc0

Tx prefix hash: 3b0e03aeb85a19af16c764048b98224fb403a65659a2b65054cc272266d32c35
Tx public key: 773c185cf3906fa60ebf582b490245f8f686474c93acca9d7f906e1d60900d81
Timestamp: 1747552373 Timestamp [UCT]: 2025-05-18 07:12:53 Age [y:d:h:m:s]: 00:224:15:09:59
Block: 1285449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158296 RingCT/type: yes/0
Extra: 01773c185cf3906fa60ebf582b490245f8f686474c93acca9d7f906e1d60900d810211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 037da249f33b2fb006c491339cee444a7a6c333836e7ec7c8c4dc20b5e0747a9 0.600000000000 1772914 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": 1285459, "vin": [ { "gen": { "height": 1285449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "037da249f33b2fb006c491339cee444a7a6c333836e7ec7c8c4dc20b5e0747a9" } } ], "extra": [ 1, 119, 60, 24, 92, 243, 144, 111, 166, 14, 191, 88, 43, 73, 2, 69, 248, 246, 134, 71, 76, 147, 172, 202, 157, 127, 144, 110, 29, 96, 144, 13, 129, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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